home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d13
/
lnmdm.arc
/
HELP.DOC
< prev
next >
Wrap
Text File
|
1991-11-12
|
10KB
|
186 lines
Cross Communications Company
LAN+MODEM User Self-help Guide
June, 1991
This information has been prepared in an effort to help users locate
and correct problems with installation and usage of the software
included in the LAN+MODEM package.
In several places the term 'COMMnn' is used and refers to the network
name which the programs use. The 'nn' refers to a numeric designation
in the range '01' to '20' depending on the maximum drivers supported
by your package.
1. In what area are you having trouble?
1.1. Specific problems
1.1.1. NETDEV or UCOM can't locate MCOM driver name(s) - Go to
section 2.
1.2. General problems
1.2.1. MCOM - Go to section 3.
1.2.2. MULTICOM - Go to section 4.
1.2.3. NETDEV - Go to section 5.
1.2.4. UCOM - Go to section 6.
1.2.5. Using third-party INT14 Software - Go to section 7.
2. NETDEV or UCOM can't locate MCOM driver name(s).
2.1. When MCOM installs do you see the message 'now resident as
network name COMMnn'?
2.1.1 If No, go to section 3.
2.2 Make sure NETDEV or UCOM displays the message 'Calling
COMMnn' where nn is the same number as MCOM displays.
2.2.1 If No, change the '/START=' command for NETDEV or add
'COMMnn' to the command line for UCOM.
2.3 If 'Calling COMMnn' message is followed by 'In Use' or 'Remote not
listening' or 'Timeout' then that particular MCOM driver is in
use. Try another.
2.4 Are you trying to connect over a bridge?
2.4.1. No - Go to section 100.
2.4.2. Yes - What type of network are you using?
2.4.2.1. NetBIOS - If MCOM is on the other side of a bridge
from NETDEV or UCOM, then the bridge is not compatible or is
not known to NetBIOS. Check your LAN software installation.
Generally if a server disk can be shared on both sides of a
bridge then LAN+MODEM should work. If your bridged LANs are
not sharing resources, try and set them up so they do and try
LAN+MODEM again. If they are, go to section 100.
2.4.2.2. IPX/SPX - Check the documentation for the use of the
NETEDIT utility. This must be used whenever your network
addresses are not 1, 2, or 3. NETEDIT and IPXSTAT should both
be moved from the UTIL subdirectory to the directory where
MCOM, UCOM, and NETDEV are located; ignore the layout of the
distribution diskette. Remove all other copies of these files
from the file server. Then use IPXSTAT and NETEDIT to properly
code your network addresses into the programs. Only when this
is done should copies of the programs be made for use on
workstation boot disks or other locations that will not read
the programs updated on the file server. If MCOM was run
before these steps were taken, reboot the respective machines
with the updated copies of MCOM. If you are still having
problems, go to section 100.
Cross Communications Company
LAN+MODEM User Self-help Guide
June, 1991
3. Problems with MCOM
3.1. The problem is with initialization (when executing).
3.1.1 First of all you must know which serial port you wish to
have shared. If you are trying to use a port and MCOM says 'in
use' then there is another program which is using that port or
IRQ. Common conflicts include mouse, LAN, or FAX cards at IRQ4
or IRQ3. Anytime another TSR is using a port, that port is
unavailable for use by LAN+MODEM. If MCOM says 'not found' then
the port could not be addressed at the standard address or IRQ
(interrupt request) for it. The values MCOM uses are:
Port Address (Hex) IRQ
COM1: 3F8 4
COM2: 2F8 3
COM3: 3E8 4
COM4: 2E8 3
Note that only two ports can be shared since only two IRQs can
be used on each computer.
3.1.2 Be sure to type 'MCOM 2' to use COM2 and skip COM1 when it is
used for another function.
3.1.3 If you have checked all these things and are still having
problems, go to section 100.
3.2. The problem is with operation (resident as TSR):
3.2.1 If the problem arises before a connection is attempted with
NETDEV or UCOM, make sure no other communications or serial
driver TSRs are attempting to use the same COM port as MCOM. If
not, go to section 100.
3.2.2 If the problem arises when running NETDEV or UCOM, see the
section appropriate for that program (5. or 6.).
3.3. Other problem - See section 100.
4. Problems with MULTICOM
4.1 MULTICOM won't install
4.1.1 NetBIOS version: If you see the message 'Name Table Full'
it indicates that your NetBIOS shell for this machine must be
reconfigured. Check your LAN manual for instructions on
increasing the size of the NetBIOS name table.
4.1.2 IPX/SPX version: If you see the message 'Socket Table Full'
it indicates that your NETx.COM shell (x = DOS version, 3 or 4)
for this machine must be reconfigured. This is done by creating
a file named 'SHELL.CFG' which resides in the same directory as
your NETx.COM file. It needs one text line which reads 'IPX
SOCKETS = 50'. Once done, reboot the computer for the setting to
go into effect, and then run MULTICOM again.
4.2 If the problem arises when running NETDEV or UCOM, see the
section appropriate for that program (5. or 6.).
4.3. Other problem - See section 100.
5. Problems with NETDEV
5.1. Not receiving any data?
5.1.1. You should use NETDEV, then (optional) NETDEV /START=nn,
and finally NETDEV /OPEN to open a channel to the MCOM driver.
You must get the message 'Available' before the channel is
actually opened.
5.1.2. If you see the message 'Available' when opening a NETDEV
channel, see section 6. for UCOM problems.
5.1.3. If not, see section 2. for connection problems.
5.2. Other problem - See section 100.
Cross Communications Company
LAN+MODEM User Self-help Guide
June, 1991
6. Problems with UCOM
6.1. Not receiving any data? (cursor sits at Initializing Modem: )
6.1.1. If you are not using a modem on this channel (rare) then
the device or host you are connected to is probably off-line.
6.1.2. If you are using a modem, as you press any keys you should
see the TX indicator blinking on the right side of the status
line. You may need to adjust your monitor's contrast control. If
not blinking, go to section 100.
6.1.3. In the center of the status line should be the label
'COMMnn' which indicates which MCOM driver to which you are
connected. If you see the word 'FLOW' instead then you are in a
flow control 'hold mode'. This should only be momentary. If it
continues, it means that the CTS signal into MCOM is being held
'off', which indicates that your cable is missing the wire for
this signal or the device MCOM is connected to does not output a
signal on this wire. In the first case you will need a cable
with control signals RTS, CTS, DTS, DSR, CD, and RI connected.
In the second case, the device or cable will need to be changed
so that CTS is driven to the 'on' level.
6.1.4. (NETDEV only: use the utility program TERM.COM. If the
label CTS 0 is shown for any length of time it indicates the
flow control 'hold mode' problem as for UCOM in the previous
paragraph).
6.1.5. If none of these problems are present, go to section 100.
6.2. Other problem - See section 100.
7. Problems with third party INT14 software
7.1. Not receiving any data?
7.1.1. You should use NETDEV, then (optional) NETDEV /START=nn,
and finally NETDEV /OPEN to open a channel to the MCOM driver.
You must get the message 'Available' before the channel is
actually opened.
7.1.2. If you do not see the message 'Available' when opening a
NETDEV channel, see section 1 for connection problems.
7.1.3. Check the Manual Appendix E and the file README.DOC for
any specific instructions for using your package with LAN+MODEM.
It must specifically be written to use 'software interrupt' 14
to read and write data. Some packages use only INT14 (eg.
PROCOMM PLUS Network Version) while others must be configured to
use it (eg. CROSSTALK Mk. 4). Check the manual for your package
to make sure it is configured for use with INT14.
7.1.4. If you are still having problems, see section 4.1 for UCOM
problems.
7.2. Other problem - See section 100.
100. Unable to resolve problem using this guide
100.1. Try another modem and cable if possible. For data problems
it is usually better to have an external modem available for
testing since the status lights can be used to diagnose problems.
100.2. If this doesn't help, Contact CCC for technical support.
Please have your serial number handy.
- end -